1 simulated user executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.

25 simulated users executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.

25 simulated users executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.

25 simulated users executing back to back sessions. Warmup or cooldown sessions (that are desaturated) start before or end after the vertical dotted line. Note that narrower event bars mean better performance.

3 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~141s). Sessions should end around the same time as each other for consistent behavior.

79 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~141s). Sessions should end around the same time as each other for consistent behavior.

83 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~141s). Sessions should end around the same time as each other for consistent behavior.

83 maintenance sessions ordered from fastest to slowest completion time. The red line marks how long the original recording session took to complete (~141s). Sessions should end around the same time as each other for consistent behavior.

Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.

Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.

Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.

Each session is represented with a line that cascades downward from each event. As time progresses, the line will move to the right. Consistent behavior will be represented with parallel lines, whereas inconsistent behavior will have lines jut arbitrarily to the right. Warmup and cooldown sessions are included as grey lines.

Total HTTP and supporting files (JS/CSS) latency (load time) is displayed for each session and run combination. Each vertical bar represents the amount of time a session's Shiny application had to wait before it is able to ask the server for information. A resonable amount of time to wait as been set to 5s. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.

Maximum WebSocket latency (calculation time) is displayed for each session and run combination. The maximum time is shown to convey the longest amount of time a user would have to wait for a response from the Shiny server. Warmup and cooldown sessions are displayed outside the dotted maintenance period lines.

Event plots are arranged by the slowest maximum time within each plot.

slowest maximum times

Event plots are arranged by the slowest minimum time within each plot.

slowest minimum times

Event plots are arranged by the largest difference in the run’s mean event time.

largest mean differences

Label Max time Min time Mean Difference
Event 53) Updated: major, minor, risk, limeStudent 4.432 0.098 1.414
Event 1) Get: Homepage 4.358 0.035 0.505
Event 47) Updated: limeStudent 3.638 0.021 1.360
Event 57) Updated: gtStudentBin, gtStudentNum 3.517 0.318 0.552
Event 41) Updated: gtStudentBin, gtStudentNum 3.469 0.313 0.609
Event 28) Updated: major, minor, risk, limeStudent 3.055 0.102 1.085
Event 39) Updated: major, minor, risk, limeStudent 2.958 0.096 1.087
Event 45) Updated: gtStudentBin, gtStudentNum, major, minor, risk 2.732 0.390 0.586
Event 55) Updated: major, minor, risk, limeStudent 2.426 0.096 1.272
Event 22) Initialize Session 1.662 0.000 0.062
Event 23) Updated: student_select 1.658 0.253 0.068
Event 30) Updated: gtStudentBin, gtStudentNum 1.632 0.315 0.337
Event 14) Get: rstudio.png 0.866 0.009 0.028
Event 8) Get: shiny.min.js 0.550 0.010 0.034
Event 2) Get: json2-min.js 0.399 0.009 0.026
Event 6) Get: simplex.min.css 0.337 0.011 0.014
Event 9) Get: bootstrap.min.js 0.190 0.009 0.007
Event 15) Get: Open_Sans_400.ttf 0.146 0.011 0.010
Event 10) Get: html5shiv.min.js 0.145 0.009 0.006
Event 18) Start Session 0.134 0.002 0.007
Event 17) Get: Connection Information 0.130 0.004 0.005
Event 11) Get: respond.min.js 0.085 0.008 0.003
Event 13) Get: shiny-server-client.js 0.052 0.012 0.014
Event 3) Get: jquery.min.js 0.033 0.010 0.007
Event 4) Get: shiny.css 0.031 0.009 0.011
Event 5) Get: bootstrap.min.css 0.025 0.011 0.006
Event 12) Get: sockjs-0.3.min.js 0.025 0.007 0.008
Event 16) Get: Shiny Token 0.024 0.004 0.010
Event 7) Get: rstudio-connect.css 0.017 0.005 0.002
Event 19) Start Connection 0.012 0.000 0.001

Event plots are arranged by the largest slope magnitude found when fitting a line to each run.

largest slope magnitudes

Event plots are arranged by the largest intercept magnitude found when fitting a line to each run

largest intercept magnitudes

Event plots are arranged by the largest error magnitude found when fitting a line to each run.

largest error magnitudes

Label Slope Intercept Error
Event 1) Get: Homepage -1.601 38.668 3.477
Event 39) Updated: major, minor, risk, limeStudent -1.543 38.725 1.562
Event 45) Updated: gtStudentBin, gtStudentNum, major, minor, risk -1.339 34.296 1.592
Event 53) Updated: major, minor, risk, limeStudent -1.207 31.559 2.437
Event 57) Updated: gtStudentBin, gtStudentNum -1.144 29.347 2.190
Event 55) Updated: major, minor, risk, limeStudent -1.027 26.995 0.989
Event 22) Initialize Session -0.623 15.605 1.316
Event 30) Updated: gtStudentBin, gtStudentNum -0.468 12.077 0.974
Event 47) Updated: limeStudent -0.374 10.703 2.090
Event 23) Updated: student_select -0.273 7.194 1.164
Event 41) Updated: gtStudentBin, gtStudentNum 0.267 -5.707 2.500
Event 2) Get: json2-min.js -0.070 1.705 0.347
Event 28) Updated: major, minor, risk, limeStudent 0.051 -0.970 2.756
Event 18) Start Session -0.036 0.906 0.076
Event 17) Get: Connection Information -0.024 0.578 0.089
Event 15) Get: Open_Sans_400.ttf -0.017 0.430 0.106
Event 10) Get: html5shiv.min.js -0.013 0.320 0.119
Event 14) Get: rstudio.png -0.007 0.175 0.825
Event 3) Get: jquery.min.js -0.005 0.136 0.010
Event 9) Get: bootstrap.min.js -0.005 0.137 0.169
Event 13) Get: shiny-server-client.js -0.003 0.099 0.021
Event 8) Get: shiny.min.js -0.003 0.092 0.502
Event 5) Get: bootstrap.min.css -0.003 0.076 0.010
Event 19) Start Connection -0.003 0.066 0.008
Event 11) Get: respond.min.js -0.002 0.071 0.071
Event 7) Get: rstudio-connect.css -0.002 0.056 0.010
Event 6) Get: simplex.min.css -0.002 0.076 0.312
Event 4) Get: shiny.css -0.002 0.058 0.008
Event 12) Get: sockjs-0.3.min.js -0.002 0.050 0.015
Event 16) Get: Shiny Token -0.001 0.028 0.009